Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Snyk] Security upgrade mkdocs-material from 8.1.3 to 9.5.32 #6

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade mkdocs-material from 8.1.3 to 9.5.32 #6

wants to merge 1 commit into from

Conversation

Sackstools
Copy link
Owner

@Sackstools Sackstools commented Sep 3, 2024 •
edited by qodo-merge-pro bot
Loading

User description

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • docs/_klipper3d/mkdocs-requirements.txt

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

PR Type

dependencies

Description

  • Updated the mkdocs-material dependency in docs/_klipper3d/mkdocs-requirements.txt from version 8.1.3 to 9.5.32 to address security vulnerabilities.
  • This change is intended to reduce vulnerabilities as identified by Snyk.

Changes walkthrough 📝

Relevant files
Dependencies
mkdocs-requirements.txt
Update mkdocs-material to fix security vulnerabilities     

docs/_klipper3d/mkdocs-requirements.txt

  • Updated mkdocs-material dependency from version 8.1.3 to 9.5.32.
  • Aimed to fix vulnerabilities related to mkdocs-material.
    		•  +1/-1     

    💡 PR-Agent usage:
    Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

    @qodo-merge-pro Qodo Merge Pro
    Copy link

    qodo-merge-pro bot commented Sep 3, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    PR Reviewer Guide 🔍

    ⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪
    🧪 No relevant tests
    🔒 No security concerns identified
    ⚡ No key issues to review

    @qodo-merge-pro Qodo Merge Pro
    Copy link

    qodo-merge-pro bot commented Sep 3, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    PR Code Suggestions ✨

    No code suggestions found for the PR.

    @qodo-merge-pro Qodo Merge Pro
    Copy link

    qodo-merge-pro bot commented Sep 3, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: build

    Failed stage: Test [❌]

    Failed test name: ""

    Failure summary:

    The action failed because the pru-gcc command was not found during the build process. This caused
    the make command to fail when trying to compile src/sched.c into out/src/sched.o.

    Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

2772:  ln -sf /home/runner/work/klipper_chronos/klipper_chronos/src/generic out/board-generic/board
2773:  make[1]: Leaving directory '/home/runner/work/klipper_chronos/klipper_chronos'
2774:  Building out/autoconf.h
2775:  mkdir -p out/
2776:  KCONFIG_AUTOHEADER=out/autoconf.h python3 lib/kconfiglib/genconfig.py src/Kconfig
2777:  Compiling out/src/sched.o
2778:  pru-gcc -Iout/ -Isrc -Iout/board-generic/ -std=gnu11 -O2 -MD -Wall -Wold-style-definition -Wtype-limits -ffunction-sections -fdata-sections -fno-delete-null-pointer-checks -flto -fwhole-program -fno-use-linker-plugin -ggdb3 -Os -minrt -mmcu=am335x.pru1 -Ilib/pru_rpmsg/include -Ilib/pru_rpmsg/include/am335x -c src/sched.c -o out/src/sched.o
2779:  make: pru-gcc: Command not found
2780:  make: *** [Makefile:64: out/src/sched.o] Error 127
2781:  ##[error]Process completed with exit code 2.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @qodo-merge-pro Qodo Merge Pro
    Copy link

    qodo-merge-pro bot commented Sep 3, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: build

    Failed stage: Test [❌]

    Failed test name: ""

    Failure summary:

    The action failed because the pru-gcc command was not found during the build process. This caused
    the make command to fail when attempting to compile src/sched.c into out/src/sched.o.

    Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

2771:  ln -sf /home/runner/work/klipper_chronos/klipper_chronos/src/generic out/board-generic/board
2772:  make[1]: Leaving directory '/home/runner/work/klipper_chronos/klipper_chronos'
2773:  Building out/autoconf.h
2774:  mkdir -p out/
2775:  KCONFIG_AUTOHEADER=out/autoconf.h python3 lib/kconfiglib/genconfig.py src/Kconfig
2776:  Compiling out/src/sched.o
2777:  pru-gcc -Iout/ -Isrc -Iout/board-generic/ -std=gnu11 -O2 -MD -Wall -Wold-style-definition -Wtype-limits -ffunction-sections -fdata-sections -fno-delete-null-pointer-checks -flto -fwhole-program -fno-use-linker-plugin -ggdb3 -Os -minrt -mmcu=am335x.pru1 -Ilib/pru_rpmsg/include -Ilib/pru_rpmsg/include/am335x -c src/sched.c -o out/src/sched.o
2778:  make: pru-gcc: Command not found
2779:  make: *** [Makefile:64: out/src/sched.o] Error 127
2780:  ##[error]Process completed with exit code 2.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @qodo-merge-pro Qodo Merge Pro
    Copy link

    qodo-merge-pro bot commented Sep 3, 2024

    PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

    CI Failure Feedback 🧐

    Action: build

    Failed stage: Test [❌]

    Failure summary:

    The action failed because the pru-gcc command was not found during the build process. This caused
    the make command to fail when trying to compile src/sched.c into out/src/sched.o.

    Relevant error logs: 
    1:  ##[group]Operating System
2:  Ubuntu
...

2782:  ln -sf /home/runner/work/klipper_chronos/klipper_chronos/src/generic out/board-generic/board
2783:  make[1]: Leaving directory '/home/runner/work/klipper_chronos/klipper_chronos'
2784:  Building out/autoconf.h
2785:  mkdir -p out/
2786:  KCONFIG_AUTOHEADER=out/autoconf.h python3 lib/kconfiglib/genconfig.py src/Kconfig
2787:  Compiling out/src/sched.o
2788:  pru-gcc -Iout/ -Isrc -Iout/board-generic/ -std=gnu11 -O2 -MD -Wall -Wold-style-definition -Wtype-limits -ffunction-sections -fdata-sections -fno-delete-null-pointer-checks -flto -fwhole-program -fno-use-linker-plugin -ggdb3 -Os -minrt -mmcu=am335x.pru1 -Ilib/pru_rpmsg/include -Ilib/pru_rpmsg/include/am335x -c src/sched.c -o out/src/sched.o
2789:  make: pru-gcc: Command not found
2790:  make: *** [Makefile:64: out/src/sched.o] Error 127
2791:  ##[error]Process completed with exit code 2.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Reviewers
    No reviews
    Assignees
    No one assigned
    Labels
    Dependencies Review effort [1-5]: 1
    Projects
    None yet
    Milestone
    No milestone
    Development

    Successfully merging this pull request may close these issues.
    2 participants
    @Sackstools @snyk-bot